-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for bitcode iOS SDK #9
Conversation
I asked about this back in december. The answer at that time was that a part of the MobilePay SDK is the OpenSSL SDK, and it doesn't support Bitcode. I'm not aware if that has changed in OpenSSL in the last 6 months, but I think the MobilePay SDK team want to support Bitcode if they could - so guess it will come when it's all their dependencies supports Bitcode. |
Thanks for providing that information @PelleRavn Compiling OpenSSL with bitcode enabled should be supported, I dont know which script the MobilePay team uses to compile OpenSSL but if there are using https://github.com/x2on/OpenSSL-for-iPhone it should work out of the box. I really hope the team will consider looking into this again. |
Any update on this? Maybe from @duytv? |
Please provide a new build with bitcode enabled. |
Please provide a version of your SDK with bitcode enabled. Currently all apps that support MobilePay will have to disable bitcode which is unheard of. |
I'll see if it works for me. Let's hope |
Thanks for your comments. We have added support for Bitcode in version 1.8.1. |
@christiankm It looks like the latest version (2.2.0) doesn't have bitcode enabled. Is it intentional that it was disabled again? |
Hi @simonbs, |
@simonbs It seems that Bitcode is enabled. What errors are you seeing? |
This is a request for you to enabled bitcode for the iOS SDK. I realise that this way of requesting it is a little odd but I thought it was worth a shot!
Apps using your framework must currently disable bitcode since MobilePay-AppSwitch-SDK has it disabled. Apple will most likely require bitcode in the future so enabling it is the right choice going forward.